Repository navigation
Release 6.3.5 with ownership kept at the change - #150
Merged
Merged
Conversation
The kernel now asks every change to extend the code that owns a behavior instead of copying it, and a replacement to migrate in-repository callers and remove the old path, shims, and the guidance it makes stale. Technical design scopes compatibility to consumers a change cannot update and prefers a failing check where an owner must hold; operations keeps guidance to what code cannot show. The runtime size gate counts raw characters against 9,900, the failing shell read that still truncates, instead of a numbered view no reader uses. Two unrun corpus scenarios share a new owned-behavior fixture whose grader-only oracles separate reuse from a copy and retirement from a shim. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Review found the kernel's removal rule broader than the playbook's compatibility scope, the guidance method unreachable from its trigger, the size-gate margin overstated, and an oracle that accepted a second implementation kept at the partner entry. The kernel now removes only paths and shims no outside consumer needs and opens operations before writing repository guidance; the gate states its short-error margin; the oracle requires the partner entry to follow the clock module. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Broad simplification audits of two governed projects kept finding refactoring debt (29 and 43 findings). Tracing the consequential findings to their origin showed three mechanisms: replacements that kept in-repository shims and re-exports, new copies of rules an existing module already owned, and guidance left stale after the code changed. The method against this lived only in
technical-design, which loaded in 17 of 88 root sessions and 3 of 156 delegates, while the kernel reached nearly every edit.Adaptive technical leadership): extend the code that owns a behavior instead of copying it. A replacement migrates in-repository callers and removes the old path and shims no outside consumer needs, and guidance it makes stale. The operations trigger now fires before writing repository guidance.scripts/check.pycounts raw characters against 9,900 instead of chars + 7 per line against 10,000. Read showed a 36.7 KB file whole, 545 of 569 recorded shell reads of the kernel were unnumbered, and a failing shell command is still cut near 10,000 characters. The gate keeps room for a short error line.owned-rule-reused-for-new-guard,replacement-retires-old-path) on a newowned-behaviorfixture with grader-only oracles; deterministic tests show each oracle accepts a complete change and rejects a copied rule, a re-export shim, a stale pointer, a removed partner entry, and a second partner implementation.Validation
python scripts/check.py, final candidate8918ed7)git diff --checkdocs/evidence.md; new cases unrunIndependent review: two isolated read-only Codex rounds. Round 1 returned four qualifying findings (kernel removal scope, unreachable guidance method, overstated gate margin, oracle accepting a second partner implementation), all fixed in
8918ed7. Round 2 returned no qualifying findings.🤖 Generated with Claude Code